Information Technology as Coordination Infrastructure

Business information technology is traditionally viewed as information provision technology. In this view, organizations use their IT to implement databases that provide people with information when they want it. This view is persistent even though information provision is never an end in itself but always has the further purpose to support the coordination of activities of people. The role if IT as coordination technology became more prominent in the 1980s with the advent of network technology, that allowed activities across different businesses to be coordinated. This trend has accellerated since the growth of Internet usage, and today IT is used to support an increasingly varied range of processes performed by a variety of partners that do not all have a hierarchical relation to each other. This makes it difficult to analyze requirements for IT support and specify IT solutions: Business processes may not be well-defined, and interests of different businesses may clash. This report argues that to deal with this in requirements engineering and IT solution specification, business information technology should not be viewed as IT support for business processes but as IT support for the coordination of activities in one or more businesses. We will identify three basic coordination mechanisms, namely coordination by price, by management, and by shared norms, and for each of these mechanisms, we will identify requirements for IT support. The advent of flexible and standardized networking technology has facilitated the creation of novel coordination mechanisms within these three general paradigms, and we will give an inventory of generalized coordination mechanisms made possible by current IT. Finally, we will draw conclusions for requirements engineering methods for IT support for each of the coordination mechanisms identified by the framework

Value-Oriented Design of Service Coordination Processes: Correctness and Trust

The rapid growth of service coordination languages creates a need for methodological support for coordination design. Coordination design differs from workflow design because a coordination process connects different businesses that can each make design decisions independently from the others, and no business is interested in supporting the business processes of others. In multi-business cooperative design, design decisions are only supported by all businesses if they contribute to the profitability of each participating business. So in order to make coordination design decisions supported by all participating businesses, requirements for a coordination process should be derived from the business model that makes the coordination profitable for each participating business. We claim that this business model is essentially a model of intended value exchanges. We model the intended value exchanges of a business model as e3 -value value models and coordination processes as UML activity diagrams. The contribution of the paper is then to propose and discuss a criterion according to which a service coordination process must be correct with respect to a value exchange model. This correctness is necessary to gain business support for the process. Finally, we discuss methodological consequences of this approach for service coordination process design

Final report on the farmer's aid in plant disease diagnoses

This report is the final report on the FAD project. The FAD project was initiated in september 1985 to test the expert system shell Babylon by developing a prototype crop disease diagnosis system in it. A short overview of the history of the project and the main problems encountered is given in chapter 1. Chapter 2 describes the result of an attempt to integrate JSD with modelling techniques like generalisation and aggregation and chapter 3 concentrates on the method we used to elicit phytopathological knowledge from specialists. Chapter 4 gives the result of knowledge acquisition for the 10 wheat diseases most commonly occurring in the Netherlands. The user interface is described briefly in chapter 5 and chapter 6 gives an overview of the additions to the implementation we made to the version of FAD reported in our second report. Chapter 7, finally, summarises the conclusions of the project and gives recommendations for follow-up projects

The place of expert systems in a typology of information systems

This article considers definitions and claims of Expert Systems ( ES) and analyzes them in view of traditional Information systems (IS). It is argued that the valid specifications for ES do not differ fran those for IS. Consequently the theoretical study and the practical development of ES should not be a monodiscipline. Integration of ES development in classical mathematics and computer science opens the door to existing knowledge and experience. Aspects of existing ES are reviewed from this interdisciplinary point of view

Requirements analysis of the VoD application using the tools in TRADE

This report contains a specification of requirements for a video-on-demand (VoD) application developed at Belgacom, used as a trial application in the 2RARE project. The specification contains three parts: an informal specification in natural language; a semiformal specification consisting of a number of diagrams intended to illustrate the informal specification; and a formal specification that makes the requiremants on the desired software system precise. The informal specification is structured in such a way that it resembles official specification documents conforming to standards such as that of IEEE or ESA. The semiformal specification uses some of the tools in from a requirements engineering toolkit called TRADE (Toolkit for Requirements And Design Engineering). The purpose of TRADE is to combine the best ideas in current structured and object-oriented analysis and design methods within a traditional systems engineering framework. In the case of the VoD system, the systems engineering framework is useful because it provides techniques for allocation and flowdown of system functions to components. TRADE consists of semiformal techniques taken from structured and object-oriented analysis as well as a formal specification langyage, which provides constructs that correspond to the semiformal constructs. The formal specification used in TRADE is LCM (Language for Conceptual Modeling), which is a syntactically sugared version of order-sorted dynamic logic with equality. The purpose of this report is to illustrate and validate the TRADE/LCM approach in the specification of distributed, communication-intensive systems

Design science, engineering science and requirements engineering

For several decades there has been a debate in the computing sciences about the relative roles of design and empirical research, and about the contribution of design and research methodology to the relevance of research results. In this minitutorial we review this debate and compare it with evidence about the relation between design and research in the history of science and technology. Our review shows that research and design are separate but concurrent activities, and that relevance of research results depends on problem setting rather than on rigorous methods. We argue that rigorous scientific methods separate design from research, and we give simple model for how to do this in a problem-driven way

Towards Information Systems Design for Value Webs

In this paper we discuss the alignment between a business model of a value web and the information systems of the participating companies needed to implement the business model. Traditional business-IT alignment approaches\ud focus on one single company, but in a value web we are dealing with various independent businesses. Since a value web is actually a web of services, delivered by IT systems owned by different companies, to ensure alignment we need to\ud specify the services and their properties and then map them on the available IT support in the different companies. Such mappings have to be evaluated in terms of their impact on the profitability of participating in the value web of the different companies. We propose techniques to map services to IT support and show how to do commercial trade-offs

Towards the Integration of Value and Coordination Models - Position Paper -

Cross-organizational collaborations have a high complexity.\ud Modelling these collaborations can be done from di®erent perspectives.\ud For example, the value perspective represents expected value exchanges\ud in a collaboration while the coordination perspective represents the order\ud in which these exchanges occur. How to maintain consistency between\ud di®erent models during design time as well as runtime constitutes a chal-\ud lenging topic. De¯ning criteria and de¯nitions re°ecting the relation be-\ud tween these models during the entire life cycle is not straightforward.\ud Di®erent criteria are used for di®erent models since each model captures\ud a speci¯c aspect of the collaboration. In this paper we investigate the\ud challenges arising when addressing the problem of maintaining adequate\ud and consistent models of a collaboration during the entire life cycle of\ud a collaboration. We propose a framework in which we connect business\ud layer, process layer and implementation layer, presenting the direction\ud for solving this multifaceted problem. We will describe several challenges\ud we anticipate to encounter while implementing our framework